Data Preview
The Notebook feature in Yeedu provides an interactive environment for coding, data exploration and analysis in Python3, Scala and SQL. Cells execute against an attached cluster and their results render inline, immediately beneath the cell that produced them, without any separate output window to switch between.
Preview output belongs to an individual cell rather than to the notebook collectively. Execute a cell a second time and we replace whatever was rendered previously.
Where Results Appear
Each executed cell renders its output in the results pane below the cell. The output area carries a Details icon on the left and an expansion toggle on the right, so a result set considerably wider than the editor column doesn't have to remain constrained at that width. Because every cell maintains its own output area, a notebook you've been developing incrementally will usually contain a mixture of freshly generated previews and older ones left over from earlier executions, and the timestamps in each header chip are what distinguish them. That distinction matters most when you're reading somebody else's notebook, where the ordering of the cells tells you nothing reliable about the ordering of the runs that produced the visible output.
Run Details on a Cell
We report each cell's run details in its own header chip, showing an execution time such as 0.187s. Those details describe that individual execution, so two cells within the same notebook can legitimately report different users and different timestamps:
- Execution Time : for example
Execution Time: 0.187s - Run By : the user who ran the cell
- Last Run : the timestamp of the last execution
The execution counter, for example [ 3 ], shows the order in which the cell last ran. It's a running count maintained for the session rather than a positional line number, so a cell you've re-executed repeatedly while developing carries a higher number than cells positioned underneath it.
Clearing a Preview
Use the trash icon on the editor top bar (Clear All Outputs) to clear every rendered output throughout the notebook.
This clears the previews only. Your code stays exactly as you left it.